Remote vehicle system configuration, control, and telematics

ABSTRACT

A vehicle control system (VCS) includes external communication interfaces, such as a Bluetooth interface, for communicating with a user communication and control device, such as a smart phone or a tablet. The user is enabled to operate certain features of the vehicle, such as the remote start, power locks/trunk, climate control, and security features, through the smart phone. The VCS may also communicate with a remote server via the user&#39;s smartphone, for example, providing telematics data and receiving service reminders for display to the user on the smartphone, the VCS, or a display built into the vehicle. The VCS may be custom installed in the vehicle using the user&#39;s or the installer&#39;s smartphone, without a physical connection from the VCS to the smartphone.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 17/211,702, entitled REMOTE VEHICLE SYSTEMCONFIGURATION. CONTROL, AND TELEMATICS, filed Mar. 24, 2021, nowallowed; which is a continuation of and claims priority to U.S. patentapplication Ser. No. 16/900,804, entitled REMOTE VEHICLE SYSTEMCONFIGURATION, CONTROL, AND TELEMATICS, filed Jun. 12, 2020, now U.S.Pat. No. 10,964,205, issued Mar. 30, 2021; which is a continuation ofand claims priority to U.S. patent application Ser. No. 16/269,321,entitled REMOTE VEHICLE SYSTEM CONFIGURATION, CONTROL, AND TELEMATICS,filed Feb. 6, 2019, now U.S. Pat. No. 10,720,045, issued Jul. 21, 2020;which is a continuation of and claims priority to U.S. patentapplication Ser. No. 15/862,630, entitled REMOTE VEHICLE SYSTEMCONFIGURATION, CONTROL, AND TELEMATICS, filed Jan. 4, 2018, now U.S.Pat. No. 10,249,182, issued Apr. 2, 2019. Each of the above-referencedpatent documents is incorporated by reference in its entirety as iffully set forth herein, including Specification, Figures, Claims, andall other matter.

FIELD OF THE DISCLOSURE

This disclosure relates generally to the field of wireless configuringand reconfiguring vehicle control systems, to wireless user control ofvehicle systems, and to telematics information exchange between vehiclesand remote servers.

BACKGROUND

Vehicle control systems are typically aftermarket electronic systemsinstalled in vehicles for consumers' convenience The functionalityprovided by such systems may include remote start capability, control ofsecurity and convenience features, climate control, and others.Telematics systems include systems that allow monitoring of the vehicleusage and performance, and communicating with the vehicle and the userof the vehicle.

A need in the art exists for improved techniques for initiallyconfiguring and later reconfiguring vehicle control systems, forimproved techniques for communicating with vehicle control systems, andfor improved communication techniques with telematics systems.

SUMMARY

This document describes embodiments, variants, and examples implementingnovel techniques for addressing one or more of the needs identifiedabove, and/or other needs. Selected embodiments described in thisdocument include methods, apparatus, and articles of manufacture thatenable wireless configuration, reconfiguration, and user control ofvehicle systems; and improved connectivity to remote servers.

In an embodiment, a vehicle control system (VCS) for installation in avehicle includes a processor; an external wireless radio frequency (RF)interface; a memory module comprising non-volatile programmable memoryand storing instructions for execution by the processor; an interface tovehicle systems: a remote start module; and a bus coupling the processorto the external wireless RF interface, the memory module, the vehiclesystems interface, and the remote start module. The processor isconfigured to execute the instructions to read vehicle information thatidentifies the vehicle, to transmit through the external wireless RFinterface the vehicle information to a user control and communicationdevice (UCCD) to enable the UCCD to obtain configuration parameters forinstallation of the VCS in the vehicle, to receive through the externalwireless RF interface the configuration parameters from the UCCD, tostore the configuration parameters in the non-volatile programmablememory, and to configure the VCS in accordance with the configurationparameters.

In an embodiment, method of operating a vehicle control system (VCS)installed in a vehicle includes: reading vehicle information thatidentifies the vehicle from a memory of the vehicle; transmitting thevehicle information through an external wireless RF interface of the VCSto a user control and communication device (UCCD) to enable the UCCD toobtain configuration parameters for installation of the VCS in thevehicle; receiving through the external wireless RF interface theconfiguration parameters from the UCCD; storing the configurationparameters received from the UCCD in a non-volatile programmable memoryof the VCS; and configuring to the VCS in accordance with theconfiguration parameters.

In an embodiment, an article of manufacture includes at least onenon-volatile machine-readable storage medium with program code stored inthe at least one non-volatile machine-readable storage medium. When theprogram code is executed by a processor of a vehicle control system(VCS) installed in a vehicle, it configures the VCS to read vehicleinformation that identifies the vehicle from a memory of the vehicle; totransmit the vehicle information through an external wireless RFinterface of the VCS to a user control and communication device (UCCD)to enable the UCCD to obtain configuration parameters for installationof the VCS in the vehicle; to receive through the external wireless RFinterface the configuration parameters from the UCCD; to store theconfiguration parameters received from the UCCD in a non-volatileprogrammable memory of the VCS; and to configure the VCS in accordancewith the configuration parameters.

In an embodiment, a mobile communication device storesmachine-executable instructions, wherein the instructions configure themobile communication device to: pair with a vehicle control system (VCS)installed in a vehicle through a radio frequency (RF) link: requestvehicle information for configuring the VCS in the vehicle; transmit thevehicle information to a remote server; receive from the remote serverinformation for configuring the VCS for the vehicle; receive from a userof the UCCD responses regarding configuration of the VCS in the vehicle;and transmit to the VCS through the RF link configuration parametersbased on the responses and the information regarding configuration ofthe VCS.

Various features and aspects will be better understood with reference tothe following description, drawings, and appended claims (if any).

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates selected components of a Vehicle Control System incommunication with a User Control and Communication Device (such as asmart phone or tablet), configured in accordance with selected aspectsdescribed in this document;

FIG. 2 illustrates selected steps of a process for configuring theVehicle Control System for a particular vehicle and features, inaccordance with selected aspects described in this document;

FIG. 3 illustrates selected steps of a process for changing parameterconfiguration of the Vehicle Control System, in accordance with selectedaspects described in this document; and

FIG. 4 illustrates selected steps of a process for controlling vehiclefeatures through the User Control and Communication Device.

DETAILED DESCRIPTION

The words “embodiment.” “variant,” “example,” and similar words andexpressions as used in this document refer to a particular apparatus,process, or article of manufacture, and not necessarily to the sameapparatus, process, or article of manufacture. Thus, “one embodiment”(or a similar word/expression) used in one place or context may refer toa particular apparatus, process, or article of manufacture; the same ora similar expression in a different place or context may refer to adifferent apparatus, process, or article of manufacture. The expression“alternative embodiment” and similar words and phrases are used toindicate one of a number of different possible embodiments, variants, orexamples. The number of possible embodiments, variants, or examples isnot necessarily limited to two or any other quantity. Characterizationof an item as “exemplary” means that the item is used as an example.Such characterization does not necessarily mean that the embodiment,variant, or example is a preferred one; the embodiment, variant, orexample may but need not be a currently preferred embodiment, variant,or example. All embodiments, variants, and examples are described forillustration purposes and are not necessarily strictly limiting.

The words “couple,” “connect,” and similar words/expressions with theirinflectional morphemes, as well as similar words and phrases, do notnecessarily import an immediate or direct connection, but include withintheir meaning connections through mediate elements.

The expression “processing logic” should be understood as selectedsteps/decision blocks and/or hardware/software/firmware for implementingthe selected steps/decision blocks. “Decision block” means a step inwhich a decision is made based on some condition, and subsequent processflow is selected based on whether the condition is met or not.

Some definitions have been explicitly provided above. Other and furtherexplicit and implicit definitions and clarifications of definitions maybe found throughout this document.

FIG. 1 illustrates selected components of a vehicle control system(“VCS”) 100 in communication with a user control and communicationdevice (“UCCD”) 150 and a remote server (“RS”) 180. The VCS 100 may be,for example, a remote start system (such as remote start systems ofDirected Electronics, Inc.). The UCCD 150 may be, for example, aportable handheld communication device such as a smartphone, a tablet,and a personal digital assistant; a computer such as laptop computer anda desktop computer. The “user” of the UCCD 150 may be the user of thevehicle, and/or the installer who installs/configures/re-configures theVCS 100 in the vehicle. The UCCD may execute an application (“app”) forcommunicating with the VCS 100 and the RS 180. The application may befor allowing the user of the vehicle to control the vehicle, and/or toallow an installer to install/initialize/configure/re-configure the VCS100. The RS 180 may be, for example, a cloud-based system; it may beconfigured to receive and analyze telematics data and providefunctionality responsive to the telematics data, such as servicereminders and warnings regarding the state of the vehicle.

The VCS 100 includes a bus 105 that provides communication/networkingcapability between and among the components of the VCS 100. The bus 105may be, for example, a bus in accordance with one of the Controller AreaNetwork standards, a k a “CAN bus”; or a processor-based system bus.

The VCS 100 includes a processing module 107, for example, amicroprocessor and supporting electronics. The VCS 100 also includes amemory module 109 that can store instructions executable by theprocessing module 107; the memory module 109 may include one or morememories of same or different types, such as ROMs, PROMs, EPROMS,EEPROMS, flash memories, optical disks, magnetic storage devices, and/orother memories. In embodiments, the memory module 109 includes at leastsome programmable, non-volatile memory.

The VCS 100 also includes an interface or interfaces 110 to vehiclecontrol modules, for example, the following: an engine computer (enginecontrol module or ECM); a transmission computer (transmission controlmodule or TCM); built-in vehicle firmware; built-in security features ofthe vehicle; a telematics module; and data storage for data thatincludes the vehicle's usage and performance data, such as OBD II data(which data storage may instead be included in a telematics module.

The VCS 100 also includes a remote start module 115, which allowsstarting of the vehicle by the VCS 100, in response to appropriatecommands, for example, remote start commands received from a user of theUCCD 150. The remote start module 115 may also interact with the vehiclecontrol modules through the interfaces 110, which the remote startmodule 115 may access through the bus 105.

The VCS 100 additionally includes add-on security module 120, which mayconnect to and monitor various sensors (e.g., shock/vibration,proximity, intrusion), and which may operate and/or control variousconvenience features (e.g., power windows, power locks, power seats,steering wheel telescoping and tilt positions, audio system presets andother audio system controls).

The VCS 100 further includes an external communication interface 125,which can be, for example, a Bluetooth interface. The interface 125 canprovide communications between the UCCD 150 and the various componentsof the VCS 100 (e.g., the remote start module 115, the interfaces 110and the devices connected to the interfaces 110, the security module120, and other VCS 100 components). The external communication interface125 may also serve as a bridge between the UCCD 150 and the bus 105, andthus enable the UCCD 150 to communicate with other devices connected tothe bus 105 directly (e.g., the remote start module 115, the add-onsecurity module 120) and indirectly through the interfaces 110 (e.g.,the engine control module, transmission control module, built-in vehiclefirmware, built-in security features of the vehicle, telematics module,usage and performance data storage).

In embodiments, the interface 125 may be another type of RF interfacethat enables vehicle communications to longer distances, for example,1500 feet or one mile, and even longer distances; the other type of RFinterface may operate, for example, on the 900 MHz band. In embodiments,the interface 125 is a Bluetooth interface, and the VCS 100 furtherincludes another type of RF interface that enables vehiclecommunications to longer distances, for example, 1500 feet or one mile,and even longer distances; the other type of RF interface may operate,for example, on the 900 MHz band. In embodiments, the interface 125 is aBluetooth interface and further includes the other type of RF interfaceand/or a cellular interface that can communicate with the UCCD 150and/or the remote server 180. In embodiments, however, the VCS 100communicates with the RS 180 via the UCCD 150.

If the VCS 100 is an aftermarket system, it likely needs to beconfigured to operate properly when installed in a particular vehicle.If the VCS 100 is an OEM system, it may also need to be configured forthe vehicle. FIG. 2 illustrates selected steps of a process 200 forconfiguring the VCS 100 for the particular vehicle and selected featuresof the VCS 100.

At flow point 201, the VCS 100 is physically installed in the vehicleand connected to its various systems, such as the power supply; sensors;ECM; TCM; built-in vehicle firmware; built-in security features of thevehicle; telematics module; data storage for data that includes thevehicle's usage and performance data and other telematics data; controlsfor various convenience features (e.g., power windows, power locks,power seats, steering wheel telescoping and tilt positions, audio systempresets and other audio system controls). Power from the vehicle isprovided to the VCS 100. Additionally, the UCCD 150 (e.g., a smartphoneor tablet) is powered up and is located within such range that it cancommunicate with the VCS 100 (e.g., through the external interface 125),and executes the installer application provided for the purpose ofconfiguring the VCS 100 in the vehicle.

In step 205, the VCS 100 is put into a pairing mode with the UCCD 150.For example, the ignition of the vehicle can be turned on, and a valetbutton of the VCS 100 may be held down for a predetermined period oftime, to cause the VCS 100 to enter into the pairing mode, such as theBluetooth pairing mode; the VCS 100 and/or the UCCD 150 may signal theuser that the pairing has been accomplished. Thus, after the step 205,the UCCD 150 (here, the installers device) can communicate with the VCS100.

In step 210, the VCS 100 accesses the vehicle's systems (e.g., theECM/TCM/firmware) to read the information sufficient to configure thefunctionality of the VCS 100 for the vehicle. The information typicallyincludes at least the Vehicle identification Number (“VIN”) orequivalent information from which make, model, year, trim level, andvehicle options can be determined.

In step 215, the VCS 100 transmits to the UCCD 150 the information readin the previous step.

In step 220, the UCCD 150 communicates with the remote server (or one ofthe remote servers) 180 to obtain access to the database from which themake/model/trim/options and/or other information pertinent to theconfiguration of the VCS 100 is determined, based on the informationfrom the step 210. The database may be a proprietary one, accessibleonly with appropriate authorization or credentials. After theinstaller's log-in (verifying the authorization/credentials), the remoteserver 180 reads the vehicle's information from the UCCD 150 andresponds to the UCCD 150 with the information needed to configure theVCS 100 for the vehicle; the information may include identification ofthe correct firmware for the vehicle, and/or the correct firmwareitself.

In step 225, the installer's app running on the UCCD 150 guides theinstaller in configuring the VCS 100, based on the information receivedfrom the remote server 180. The installer may be presented with choicesand requests for information and for selections. The installer'sresponses may be stored on the UCCD 150.

In step 230, the installer's app executing on the UCCD 150 sends theinstaller's responses and/or appropriate information derived from theresponses and the information obtained from the RS 180 database (theconfiguration parameters) to the VCS 100.

In step 235, the VCS 100 stores the configuration parameters of the VCS100 in a memory of the VCS 100, such as the non-volatile memory of thememory module 109.

In step 240, the VCS 100 configures itself for the vehicle, based on theconfiguration parameters. In this step, the VCS 100 may also writeinformation into the vehicle's firmware or other systems, to completethe matchup between the VCS 100 and the vehicle.

The process may then terminate at flow point 299.

The user of the vehicle and/or the installer may wish to change some ofthe configuration parameters at a later time, that is, after the initialinstallation. This might be the case, for example, if the user decidesto purchase additional features of the VCS 100 or related services, toadd accessories, to increase runtime for remote start, or for otherreasons. The process for re-installing the VCS 100 or changing theconfiguration parameters may be quite similar to the process 200 forinitially configuring the VCS 100. FIG. 3 illustrates selected steps ofa process 300 for changing the parameter configuration. The process 300may use the installer's app or the end-user's app (the app of the userof the vehicle) executing on the UCD 100, if the end-user's app includesthe appropriate functionality. To summarize, the VCS 100 and the UCCD150 are put into a pairing mode (step 305), the app guides the end-useror the installer in re-configuring the VCS 100 (step 310), by presentingchoices and requests for information and for selections. The end-user'sor the installer's responses are stored on the UCCD 150. The UCCD 150verifies the validity/permission for the new parameters with the remoteserver 180 (step 315, for example, verifying authorization for additionof new features/services or deletion of old ones). If verified (decisionblock 320), the UCCD 150 transmits the new configuration parameters tothe VCS 100 (step 325); if not verified, the process ends (flow point399), to be repeated as needed or desired. When the VCS 100 receives thenew configuration parameters sent in the step 325, the VCS 100 storesthe changed parameters in the non-volatile memory of the memory module109 (step 330), and re-configures itself and possibly also the vehiclebased on the changed parameters (step 335). The process then terminatesin the flow point 399, to be repeated as needed or desired.

Note that in the process 300 there is no need to obtain the vehicleinformation from the database of the remote server 180, because thevehicle information is known from the time of the initial information.But in embodiments, the process also obtains the vehicle information anduses it as in the process 200.

Once the VCS 100 is installed and configured, the end-user can controlthe vehicle using the end-user's UCCD 150, running an end-userapplication. The end-user app, once opened, may automatically pair withthe VCS 100, through the Bluetooth or similar transceiver on the UCCD150 and the external interface 125 of the VCS 100; the app may thendisplay a command interface that allows the end-user to input commands,which the app transmits to the VCS 100. The commands may includecontrols of the security features of the vehicle (e.g., turn thesecurity system on/off, clear an alarm), convenience features such asthe remote start and temperature control, lights flashing and hornon/off, location interrogate (for receiving the vehicle's position atthe UCCD 150, and others. FIG. 4 illustrates selected steps of a process400 for controlling the vehicle features through the UCCD 150 app andthe VCS 100.

At flow point 401, the VCS 100 is installed in the vehicle, configured(e.g, through the process 200)), and powered up (as it would typicallybe regardless of the presence or position of the vehicle's key).Additionally, the VCS 100 is connected to the UCCD 150 through theexternal interface 125 (or one or more of the interfaces 125); and theend-user app is available on the powered up UCCD 150, which is withincommunication range of the VCS 100. Note that the communication rangemay include any cellular service accessible location, when the interface125 is or includes a cellular interface that can communicate with theUCCD 150.

In step 405, the user activates the app on the UCCD 150, for example, bytapping on the app's icon.

In step 410, the app establishes a communication link (such as acellular link, a Bluetooth link, another RF link) with the interface 125of the VCS 100. This may be done automatically upon activation of theapp, or require some deliberate action of the end-user.

In step 415, the user issues a command from the app/UCCD 150, forexample, by tapping on a particular icon of the app. In response, theapp sends a corresponding signal to the VCS 100. The signal correspondsto the icon and may instruct the VCS 100, for example, to start thevehicle remotely, to turn on the climate control system of the vehicleand/or set the temperature of the climate control system, to activatethe horn and/or siren, to flash headlights, to lock/unlock the vehicle'sdoors, to activate panic mode of the vehicle, and to perform any otherfunction for which the vehicle and the VCS 100 are configured; these, ofcourse, are just examples of the available functionalities.

In step 420, the VCS 100 receives the command.

In step 425, the VCS 100 performs the function corresponding to thecommand.

In step 430, the VCS 100 sends to the UCCD 150 an acknowledgement of theperformance of the command.

At flow point 499, the process terminates, to be repeated as needed ordesired.

The presence of the communication link between the VCS 100 and the UCCD150 with the end-user app allows the VCS 150 to communicate with theremote server 180, for example, transmitting to the remote server 180telematics data and receiving data and firmware updates from the remoteserver 180. Thus, in operation, the end-user app may run on the UCCD150, at least occasionally (e.g., continuously, continually, atpredetermined times or intervals, at random times), establishing the RFlink (such as the Bluetooth link or 900 MHz link) with the VCS 100. Whenthe link is established, the VCS 100 may transmit to the app/UCCD 150telematics and/or other data, for subsequent transmission from theapp/UCCD 150 to the remote server 180; and the app/UCCD 150 may transmitto the VCS 100 data and/or firmware updates and or interrogation requestfrom the remote server 180.

The features described throughout this document may be presentindividually, or in any combination or permutation, except where thepresence or absence of specific features (elements/limitations) isinherently required, explicitly indicated, or otherwise made clear fromthe description. This applies whether or not features appear related tospecific embodiments.

Although the process steps and decisions (if decision blocks arepresent) may be described serially in this document, certain stepsand/or decisions may be performed by same and/or separate elements inconjunction or in parallel, asynchronously or synchronously, in apipelined manner, or otherwise. There is no particular requirement thatthe steps and decisions be performed in the same order in which thisdescription lists them or the Figures show them, except where a specificorder is inherently required, explicitly indicated, or is otherwise madeclear from the context. Furthermore, not every illustrated step anddecision block may be required in every embodiment in accordance withthe concepts described in this document, while some steps and decisionblocks that have not been specifically illustrated may be desirable ornecessary in some embodiments in accordance with the concepts. It shouldbe noted, however, that specific embodiments/variants/examples use theparticular order(s) in which the steps and decisions (if applicable) areshown and/or described.

The instructions (machine executable code) corresponding to the methodsteps of the embodiments, variants, and examples disclosed in thisdocument may be embodied directly in hardware, in software, in firmware,or in combinations thereof. A software module may be stored in volatilememory, flash memory, Read Only Memory (ROM), Electrically ProgrammableROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), hard disk,a CD-ROM, a DVD-ROM, or other form of non-transitory storage mediumknown in the art. Exemplary storage medium or media may be coupled toone or more processors so that the one or more processors can readinformation from, and write information to, the storage medium or media.In an alternative, the storage medium or media may be integral to one ormore processors.

This document describes in detail the inventive apparatus, methods, andarticles of manufacture for configuring/reconfiguring and using avehicle control system. This was done for illustration purposes and,therefore, the foregoing description is not necessarily intended tolimit the spirit and scope of the invention(s) described. Neither thespecific embodiments of the invention(s) as a whole, nor those of its(or their, as the case may be) features necessarily limit the generalprinciples underlying the invention(s). The specific features describedherein may be used in some embodiments, but not in others, withoutdeparture from the spirit and scope of the invention(s) as set forthherein. Various physical arrangements of components and various stepsequences also fall within the intended scope of the invention(s). Manyadditional modifications are intended in the foregoing disclosure, andit will be appreciated by those of ordinary skill in the pertinent artthat in some instances some features will be employed in the absence ofa corresponding use of other features. The embodiments described aboveare illustrative and not necessarily limiting, although they or theirselected features may be limiting for some claims. The illustrativeexamples therefore do not necessarily define the metes and bounds of theinvention(s) and the legal protection afforded the invention(s).

What is claimed is:
 1. A vehicle control system (VCS) for installationin a vehicle, the VCS comprising: a processor and a memory modulestoring instructions for execution by the processor; a wireless radiofrequency (RF) interface to one or more external devices, the wirelessRF interface being coupled to the processor to enable the processor tocommunicate with the one or more external devices; an interface couplingthe processor to one or more vehicle systems of the vehicle; wherein theprocessor is configured to execute the instructions to: read vehicleinformation from the one or more vehicle systems, the vehicleinformation comprising an identification of the vehicle; transmitthrough the wireless RF interface the vehicle information to a mobiledevice, thereby enabling the mobile device to obtain configurationparameters for installation of the VCS in the vehicle; receive throughthe wireless RF interface the configuration parameters from the mobiledevice; and configure the VCS in accordance with the configurationparameters.
 2. The vehicle control system of claim 1, wherein: thewireless RF interface comprises a Bluetooth® transceiver; and theinterface coupling the processor to the vehicle systems comprises aController Area Network (CAN) bus.
 3. The vehicle control system ofclaim 2, wherein, after the VCS is configured in accordance with theconfiguration parameters, the processor is further configured to executethe instructions to receive one or more user commands from the mobiledevice through the wireless RF interface and, in response to eachcommand of the one or more commands received from the mobile device,activate a vehicle control function corresponding to said each command.4. The vehicle control system of claim 3, wherein the one or morecommands comprise at least one command selected from the groupconsisting of a remote start command, a command to sound a horn or asiren, a command to turn on one or more lights, a panic command, a lockdoors command, an unlock doors command, a command to turn on a securitysystem, a command to turn off the security system, a command to change aclimate control setting, a command to clear an alarm, and a command totransmit to the mobile device current location of the vehicle.
 5. Thevehicle control system of claim 1, wherein, after the VCS is configuredin accordance with the configuration parameters, the processor isfurther configured to execute the instructions to receive through theexternal wireless RF interface re-configuration parameters from themobile device, and to re-configure the VCS in accordance with there-configuration parameters.
 6. The vehicle control system of claim 1,wherein, after the VCS is configured in accordance with theconfiguration parameters, the processor is further configured to executethe instructions to receive through the external wireless RF interface asoftware update for the VCS from the mobile device, and to install thesoftware update in the VCS.
 7. The vehicle control system of claim 1,wherein, after the VCS is configured in accordance with theconfiguration parameters, the processor is further configured to executethe instructions to read telematics data from at least one of thevehicle systems and to transmit the telematics data to a remote server.8. The vehicle control system of claim 1, wherein: the wireless RFinterface comprises a Bluetooth® transceiver; and after the VCS isconfigured in accordance with the configuration parameters, theprocessor is further configured to execute the instructions to readtelematics data from at least one vehicle system and to transmit thetelematics data to a remote server through the Bluetooth®, transceiverand the mobile device.
 9. The vehicle control system of claim 1, whereinthe VCS is further configured to execute the instructions to receiveservice reminders and/or warnings regarding state of the vehicle from aremote server through the wireless RF interface.
 10. The vehicle controlsystem of claim 1, wherein the wireless RF interface comprises acellular transceiver.
 11. An apparatus comprising the VCS of claim 1 andthe mobile device.
 12. The apparatus of claim 11, further comprising: aremote server, wherein, after the VCS is configured in accordance withthe configuration parameters, the processor is further configured toexecute the instructions to read telematics data from at least onevehicle system and to transmit the telematics data to the remote server.13. The apparatus of claim 11, wherein the mobile device is configuredto: establish a communication link with the wireless RF interface of theVCS; receive the vehicle information from the wireless RF interface ofthe VCS; and obtain the configuration parameters based at least in parton responses of a user of the mobile device.
 14. The apparatus of claim11, wherein the mobile device is configured to: establish acommunication link with the wireless RF interface of the VCS; receivethe vehicle information from the wireless RF interface of the VCS;establish a communication link with one or more remote servers; andobtain the configuration parameters based at least in part on datareceived from the one or more remote servers.
 15. The apparatus of claim11, wherein the mobile device is configured to: establish acommunication link with the wireless RF interface of the VCS; receivethe vehicle information from the wireless RF interface of the VCS;establish a communication link with one or more remote servers; andobtain an identification of a software update for the VCS from the oneor more remote servers.
 16. The apparatus of claim 11, wherein themobile device is configured to: establish a communication link with thewireless RF interface of the VCS; receive the vehicle information fromthe wireless RF interface of the VCS; present a user of the mobiledevice with choices and/or requests for information; receive from theuser responses to the choices and/or requests for information; anddetermine the configuration parameters based at least in part on theuser responses.
 17. The apparatus of claim 11, wherein the mobile deviceis configured to: establish a communication link with the wireless RFinterface of the VCS; receive the vehicle information from the wirelessRF interface of the VCS; present a user of the mobile device withchoices and/or requests for information; receive from the user responsesto the choices and/or requests for information; establish acommunication link with one or more remote servers; and determine theconfiguration parameters based on data received from the one or moreremote servers and on the user responses.
 18. A method of configuring avehicle control system (VCS) installed in a vehicle, the methodcomprising: reading vehicle information by a processor of the VCS from amemory of the vehicle, the vehicle information identifying the vehicle;sending the vehicle information through an external wireless RFinterface of the VCS to a user mobile device, thereby enabling the usermobile device to obtain parameters for the VCS to be configured for thevehicle; and receiving through the external wireless RF interface theparameters from the mobile device.
 19. The method of claim 18, furthercomprising: obtaining the parameters, by the user mobile device, from aremote computer system; and transmitting the parameters by the mobiledevice to the external wireless RF interface of the VCS; wherein theparameters are of a type selected from the group consisting ofconfiguration parameters for initial configuration of the VCS, andre-configuration parameters for the VCS after initial configuration. 20.The method of claim 19, further comprising: receiving one or more usercommands from the mobile device through the wireless RF interface, bythe processor of the VCS; and, in response to each command of the one ormore commands received from the mobile device, executing a vehiclecontrol function corresponding to said each command, by the processor ofthe VCS.